Operational safety mode

ABSTRACT

The present disclosure generally relates to implementing an operational safety mode that manages the output of notifications at an electronic device when a user of the device is operating a vehicle.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationNo. 62/507,115, entitled “OPERATIONAL SAFETY MODE,” filed on May 16,2017, the contents of which are hereby incorporated by reference in itsentirety.

FIELD

The present disclosure relates generally to electronic devices, and morespecifically to techniques for operating the electronic device invarious modes in various situations.

BACKGROUND

Electronic devices can receive information, including, merely by way ofexample, communications from other users' electronic devices and/orapplications. Such electronic devices can output notificationsindicating the arrival of information.

BRIEF SUMMARY

Some operational modes involving the output of notifications usingelectronic devices, however, are generally cumbersome and inefficient.For example, some existing techniques use a complex and time-consuminguser interface, which may include multiple key presses or keystrokes.Existing techniques require more time than necessary, wasting user timeand device energy. This latter consideration is particularly importantin battery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for managing the output ofnotifications. Such methods and interfaces optionally complement orreplace other methods for managing the output of notifications. Suchmethods and interfaces reduce the cognitive burden on a user and producea more efficient human-machine interface. For battery-operated computingdevices, such methods and interfaces conserve power and increase thetime between battery charges. For battery-operated computing devices,such methods and interfaces conserve power and increase the time betweenbattery charges. For example, the methods and interfaces contemplatedherein offer reduced processing power, reduced memory usage, and reducedbattery usage by a display at the device.

Example methods are disclosed herein. An example method includes, at anelectronic device with a display: detecting one or more contextualparameters; in accordance with the one or more contextual parameterssatisfying operational safety mode initiation criteria, including acriterion that is satisfied when the contextual parameters areindicative of the electronic device being situated within an operatingmotor vehicle, initiating an operational safety mode; while the deviceis in the operational safety mode: receiving a notification; inaccordance with a determination that the notification satisfies a set ofnotification output criteria, causing output corresponding to thenotification; and in accordance with a determination that thenotification does not satisfy the set of notification output criteria,forgoing causing output corresponding to the notification.

An example method includes, at an electronic device with a display:while in an operational safety mode: receiving a communication from acontact; in accordance with a determination that the communicationsatisfies notification output criteria, including a criterion that issatisfied when the communication includes a notification output request,outputting a notification corresponding to the communication; and inaccordance with a determination that the communication does not satisfythe notification output criteria, forgoing outputting the notification.

An example method includes, while a first set of operational safety modeinitiation criteria of a plurality of sets of operational safety modeinitiation criteria is active, the first set of operational safety modeinitiation criteria including a criterion that is satisfied whenmovement of the electronic device exceeds a threshold movement value:detecting a first set of one or more contextual parameters; in responseto detecting the first set of one or more contextual parameters: inaccordance with a determination that the first set of contextualparameters satisfy the first set of operational safety mode initiationcriteria, initiating the operational safety mode; while a second set ofoperational safety mode initiation criteria of the plurality of sets ofoperational safety mode initiation criteria is active, the second set ofoperational safety mode initiation criteria including a criterion thatis satisfied when the electronic device is connected to a secondelectronic device associated with a motor vehicle: detecting a secondset of one or more contextual parameters; in response to detecting thesecond set of one or more contextual parameters: in accordance with adetermination that the second set of contextual parameters satisfy thesecond set of operational safety mode initiation criteria, initiatingthe operational safety mode; in accordance with a determination that thesecond set of contextual parameters do not satisfy the second set ofoperational safety mode initiation criteria, while satisfying the firstset of operational safety mode initiation criteria, forgoing initiatingthe operational safety mode.

Example devices are disclosed herein. An example electronic deviceincludes a display; one or more processors; and memory storing one ormore programs configured to be executed by the one or more processors,the one or more programs including instructions for: detecting one ormore contextual parameters; in accordance with the one or morecontextual parameters satisfying operational safety mode initiationcriteria, including a criterion that is satisfied when the contextualparameters are indicative of the electronic device being situated withinan operating motor vehicle, initiating an operational safety mode; whilethe device is in the operational safety mode: receiving a notification;in accordance with a determination that the notification satisfies a setof notification output criteria, causing output corresponding to thenotification; and in accordance with a determination that thenotification does not satisfy the set of notification output criteria,forgoing causing output corresponding to the notification.

An example electronic device includes a display; one or more processors;and memory storing one or more programs configured to be executed by theone or more processors, the one or more programs including instructionsfor: while in an operational safety mode: receiving a communication froma contact; in accordance with a determination that the communicationsatisfies notification output criteria, including a criterion that issatisfied when the communication includes a notification output request,outputting a notification corresponding to the communication; and inaccordance with a determination that the communication does not satisfythe notification output criteria, forgoing outputting the notification.

An example electronic device includes a display; one or more processors;and memory storing one or more programs configured to be executed by theone or more processors, the one or more programs including instructionsfor: while a first set of operational safety mode initiation criteria ofa plurality of sets of operational safety mode initiation criteria isactive, the first set of operational safety mode initiation criteriaincluding a criterion that is satisfied when movement of the electronicdevice exceeds a threshold movement value: detecting a first set of oneor more contextual parameters; in response to detecting the first set ofone or more contextual parameters: in accordance with a determinationthat the first set of contextual parameters satisfy the first set ofoperational safety mode initiation criteria, initiating the operationalsafety mode; while a second set of operational safety mode initiationcriteria of the plurality of sets of operational safety mode initiationcriteria is active, the second set of operational safety mode initiationcriteria including a criterion that is satisfied when the electronicdevice is connected to a second electronic device associated with amotor vehicle: detecting a second set of one or more contextualparameters; in response to detecting the second set of one or morecontextual parameters: in accordance with a determination that thesecond set of contextual parameters satisfy the second set ofoperational safety mode initiation criteria, initiating the operationalsafety mode; in accordance with a determination that the second set ofcontextual parameters do not satisfy the second set of operationalsafety mode initiation criteria, while satisfying the first set ofoperational safety mode initiation criteria, forgoing initiating theoperational safety mode.

Example non-transitory computer-readable storage media are disclosedherein. An example non-transitory computer-readable storage mediumstores one or more programs configured to be executed by one or moreprocessors of an electronic device with a display, the one or moreprograms including instructions for: detecting one or more contextualparameters; in accordance with the one or more contextual parameterssatisfying operational safety mode initiation criteria, including acriterion that is satisfied when the contextual parameters areindicative of the electronic device being situated within an operatingmotor vehicle, initiating an operational safety mode; while the deviceis in the operational safety mode: receiving a notification; inaccordance with a determination that the notification satisfies a set ofnotification output criteria, causing output corresponding to thenotification; and in accordance with a determination that thenotification does not satisfy the set of notification output criteria,forgoing causing output corresponding to the notification.

An example non-transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display, the one or more programs includinginstructions for: while in an operational safety mode: receiving acommunication from a contact; in accordance with a determination thatthe communication satisfies notification output criteria, including acriterion that is satisfied when the communication includes anotification output request, outputting a notification corresponding tothe communication; and in accordance with a determination that thecommunication does not satisfy the notification output criteria,forgoing outputting the notification.

An example non-transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display, the one or more programs includinginstructions for: while a first set of operational safety modeinitiation criteria of a plurality of sets of operational safety modeinitiation criteria is active, the first set of operational safety modeinitiation criteria including a criterion that is satisfied whenmovement of the electronic device exceeds a threshold movement value:detecting a first set of one or more contextual parameters; in responseto detecting the first set of one or more contextual parameters: inaccordance with a determination that the first set of contextualparameters satisfy the first set of operational safety mode initiationcriteria, initiating the operational safety mode; while a second set ofoperational safety mode initiation criteria of the plurality of sets ofoperational safety mode initiation criteria is active, the second set ofoperational safety mode initiation criteria including a criterion thatis satisfied when the electronic device is connected to a secondelectronic device associated with a motor vehicle: detecting a secondset of one or more contextual parameters; in response to detecting thesecond set of one or more contextual parameters: in accordance with adetermination that the second set of contextual parameters satisfy thesecond set of operational safety mode initiation criteria, initiatingthe operational safety mode; in accordance with a determination that thesecond set of contextual parameters do not satisfy the second set ofoperational safety mode initiation criteria, while satisfying the firstset of operational safety mode initiation criteria, forgoing initiatingthe operational safety mode.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Example transitory computer-readable storage media are disclosed herein.An example non-transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display, the one or more programs includinginstructions for: detecting one or more contextual parameters; inaccordance with the one or more contextual parameters satisfyingoperational safety mode initiation criteria, including a criterion thatis satisfied when the contextual parameters are indicative of theelectronic device being situated within an operating motor vehicle,initiating an operational safety mode; while the device is in theoperational safety mode: receiving a notification; in accordance with adetermination that the notification satisfies a set of notificationoutput criteria, causing output corresponding to the notification; andin accordance with a determination that the notification does notsatisfy the set of notification output criteria, forgoing causing outputcorresponding to the notification.

An example transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display, the one or more programs includinginstructions for: while in an operational safety mode: receiving acommunication from a contact; in accordance with a determination thatthe communication satisfies notification output criteria, including acriterion that is satisfied when the communication includes anotification output request, outputting a notification corresponding tothe communication; and in accordance with a determination that thecommunication does not satisfy the notification output criteria,forgoing outputting the notification.

An example transitory computer-readable storage medium stores one ormore programs configured to be executed by one or more processors of anelectronic device with a display, the one or more programs includinginstructions for: while a first set of operational safety modeinitiation criteria of a plurality of sets of operational safety modeinitiation criteria is active, the first set of operational safety modeinitiation criteria including a criterion that is satisfied whenmovement of the electronic device exceeds a threshold movement value:detecting a first set of one or more contextual parameters; in responseto detecting the first set of one or more contextual parameters: inaccordance with a determination that the first set of contextualparameters satisfy the first set of operational safety mode initiationcriteria, initiating the operational safety mode; while a second set ofoperational safety mode initiation criteria of the plurality of sets ofoperational safety mode initiation criteria is active, the second set ofoperational safety mode initiation criteria including a criterion thatis satisfied when the electronic device is connected to a secondelectronic device associated with a motor vehicle: detecting a secondset of one or more contextual parameters; in response to detecting thesecond set of one or more contextual parameters: in accordance with adetermination that the second set of contextual parameters satisfy thesecond set of operational safety mode initiation criteria, initiatingthe operational safety mode; in accordance with a determination that thesecond set of contextual parameters do not satisfy the second set ofoperational safety mode initiation criteria, while satisfying the firstset of operational safety mode initiation criteria, forgoing initiatingthe operational safety mode.

Thus, devices are provided with faster, more efficient methods andinterfaces for managing the output of notifications and providingcertain operational modes when certain parameters are detected, therebyincreasing the effectiveness, efficiency, and user satisfaction withsuch devices. Such methods and interfaces may complement or replaceother methods for managing the output of notifications providingoperational modes.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIGS. 5C-5D illustrate exemplary components of a personal electronicdevice having a touch-sensitive display and intensity sensors inaccordance with some embodiments.

FIGS. 5E-5H illustrate exemplary components and user interfaces of apersonal electronic device in accordance with some embodiments.

FIGS. 6A-6I illustrate examples for an operational safety mode inaccordance with some embodiments.

FIGS. 7A-7D illustrate example user interfaces during the operationalsafety mode in accordance with some embodiments.

FIG. 8 is a flow diagram illustrating an example method for anoperational safety mode, including filtering the output of notificationsbased on notification output criteria, in accordance with someembodiments.

FIG. 9 is a flow diagram illustrating another example method for anoperational safety mode, including suppressing the output ofnotifications that do not satisfy notification output criteria includinga criterion for a sender-marked output request, in accordance with someembodiments.

FIG. 10 is a flow diagram illustrating yet another example method for anoperational safety mode, including initiating the operational safetymode, in accordance with some embodiments.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for safe operation, such as initiating an operationalsafety mode based on detected contexts (e.g., environmental contexts),and for methods and interfaces for managing notifications andcommunications during the operational safety mode to promote safeoperation. Such techniques can reduce the cognitive burden on a user whoaccesses and/or otherwise receives notifications and communications,thereby enhancing productivity and safe usage of the device. Further,such techniques can reduce processor and battery power otherwise wastedon redundant user inputs.

Further, the methods and interfaces disclosed herein promote safe usageof electronic devices under certain situations, such as when theelectronic device is in a vehicle (e.g., automobile, motorcycle,aircraft, boat, bicycle, etc.) and the user of the device is operatingthe vehicle. As described herein, in some examples the device operatesin an operational safety mode that reduces the temptation to send and/orreceive communications (e.g., text messages, e-mail) and reduces theurge to check the device while driving. In some examples, theoperational safety mode is enhanced with custom behaviors tailored todriving experiences to prevent driver distraction while at the sametime, preventing the driver from appearing unresponsive tocommunications from certain users at other electronic devices. In someexamples, the device distinguishes whether the device is associated withthe driver of the vehicle who may appreciate the operational safety modeor whether the device is associated with a passenger at the vehicle whomay not necessarily need the operational safety mode. In another aspect,in some examples, the operational safety mode safe promotes safe usageand custom behaviors by providing user interfaces with larger and/orchunkier tap targets to facilitate interaction and navigation of certainapplications when various contexts are detected by and/or associatedwith the electronic device. In some examples discussed below, theelectronic device includes voice control, and during the operationalsafety mode, the voice control includes a verbose operational mode thatprovides a higher level of voice guidance, thereby further decreasingthe need for the user to glance at the device. In some examples, theoperational safety mode locks the device (e.g., locks both userinterfaces and voice control) to discourage the user from potentiallyquestionable behavior while certain contexts are detected at theelectronic device.

Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5H provide a description ofexemplary devices for performing the techniques for an operationalsafety mode. FIGS. 6A-6I illustrate examples of the operational safetymode. FIGS. 8-10 are flow diagrams illustrating methods for theoperational safety mode in accordance with some embodiments. FIGS. 6A-6Iare used to illustrate the processes described below, including theprocesses in FIGS. 8-10. FIGS. 7A-7D illustrate example user interfacesfor an operational safety mode. The user interfaces in FIGS. 7A-7D areused to illustrate the processes described below, including theprocesses in FIGS. 8-10.

This present disclose relates to U.S. Provisional patent applicationSer. No. 15/596,592, entitled, “UE Motion Estimate Based on CellularParameters,” filed on May 16, 2017, which describes systems andtechniques related to providing improved motion estimation base oncellular parameters and is hereby incorporated by reference. Forexample, U.S. Provisional patent application Ser. No. 15/596,592presents embodiments of user equipment device (UE), and associatedmethods for enabling the UE to estimate velocity of the UE based oncellular parameters. In some embodiments, a first velocity of a UE maybe estimated based on a first set of parameters associated with one ormore cellular based metrics. Doppler measurements may be performed inresponse to the first velocity exceeding a velocity threshold for atleast a time period. In some embodiments, performing (or conducting) thedoppler measurements may be triggered by (e.g., in response to) thefirst velocity exceeding the velocity threshold for at least the firsttime period and receiving an indication from a motion processor of theUE that the UE is in a non-static state. In addition, a second velocityof the UE may be estimated based on the first set of parameters and thedopper measurements.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that is,in some circumstances, otherwise not be accessible by the user on areduced-size device with limited real estate for displaying affordances(e.g., on a touch-sensitive display) and/or receiving user input (e.g.,via a touch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user. Using tactile outputs toprovide haptic feedback to a user enhances the operability of the deviceand makes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g. IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, intensity sensor controller 159,haptic feedback controller 161, and one or more input controllers 160for other input or control devices. The one or more input controllers160 receive/send electrical signals from/to other input control devices116. The other input control devices 116 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 160 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 208, FIG.2) optionally include an up/down button for volume control of speaker111 and/or microphone 113. The one or more buttons optionally include apush button (e.g., 206, FIG. 2).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsis, optionally, user-customizable. Touch screen 112 is used to implementvirtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat.No. 6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 112 displays visual output from device 100, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad (not shown) for activating ordeactivating particular functions. In some embodiments, the touchpad isa touch-sensitive area of the device that, unlike the touch screen, doesnot display visual output. The touchpad is, optionally, atouch-sensitive surface that is separate from touch screen 112 or anextension of the touch-sensitive surface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer (notshown) and a GPS (or GLONASS or other global navigation system) receiver(not shown) for obtaining information concerning the location andorientation (e.g., portrait or landscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3)stores device/global internal state 157, as shown in FIGS. 1A and 3.Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151;    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es). physicaladdress(es) or other information with a name; associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo! Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3) includes event sorter 170 (e.g., inoperating system 126) and a respective application 136-1 (e.g., any ofthe aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 136-1inherits methods and other properties. In some embodiments, a respectiveevent handler 190 includes one or more of: data updater 176, objectupdater 177, GUI updater 178, and/or event data 179 received from eventsorter 170. Event handler 190 optionally utilizes or calls data updater176, object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera,”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 800-1000(FIGS. 8-10). A computer-readable storage medium can be any medium thatcan tangibly contain or store computer-executable instructions for useby or in connection with the instruction execution system, apparatus, ordevice. In some examples, the storage medium is a transitorycomputer-readable storage medium. In some examples, the storage mediumis a non-transitory computer-readable storage medium. The non-transitorycomputer-readable storage medium can include, but is not limited to,magnetic, optical, and/or semiconductor storages. Examples of suchstorage include magnetic disks, optical discs based on CD, DVD, orBlu-ray technologies, as well as persistent solid-state memory such asflash, solid-state drives, and the like. Personal electronic device 500is not limited to the components and configuration of FIG. 5B, but caninclude other or additional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

FIG. 5C illustrates detecting a plurality of contacts 552A-552E ontouch-sensitive display screen 504 with a plurality of intensity sensors524A-524D. FIG. 5C additionally includes intensity diagrams that showthe current intensity measurements of the intensity sensors 524A-524Drelative to units of intensity. In this example, the intensitymeasurements of intensity sensors 524A and 524D are each 9 units ofintensity, and the intensity measurements of intensity sensors 524B and524C are each 7 units of intensity. In some implementations, anaggregate intensity is the sum of the intensity measurements of theplurality of intensity sensors 524A-524D, which in this example is 32intensity units. In some embodiments, each contact is assigned arespective intensity that is a portion of the aggregate intensity. FIG.5D illustrates assigning the aggregate intensity to contacts 552A-552Ebased on their distance from the center of force 554. In this example,each of contacts 552A, 552B, and 552E are assigned an intensity ofcontact of 8 intensity units of the aggregate intensity, and each ofcontacts 552C and 552D are assigned an intensity of contact of 4intensity units of the aggregate intensity. More generally, in someimplementations, each contact j is assigned a respective intensity Ijthat is a portion of the aggregate intensity, A, in accordance with apredefined mathematical function, Ij=A·(Dj/ΣDi), where Dj is thedistance of the respective contact j to the center of force, and ΣDi isthe sum of the distances of all the respective contacts (e.g., i=1 tolast) to the center of force. The operations described with reference toFIGS. 5C-5D can be performed using an electronic device similar oridentical to device 100, 300, or 500. In some embodiments, acharacteristic intensity of a contact is based on one or moreintensities of the contact. In some embodiments, the intensity sensorsare used to determine a single characteristic intensity (e.g., a singlecharacteristic intensity of a single contact). It should be noted thatthe intensity diagrams are not part of a displayed user interface, butare included in FIGS. 5C-5D to aid the reader.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

FIGS. 5E-5H illustrate detection of a gesture that includes a pressinput that corresponds to an increase in intensity of a contact 562 froman intensity below a light press intensity threshold (e.g., “IT_(L)”) inFIG. 5E, to an intensity above a deep press intensity threshold (e.g.,“IT_(D)”) in FIG. 5H. The gesture performed with contact 562 is detectedon touch-sensitive surface 560 while cursor 576 is displayed overapplication icon 572B corresponding to App 2, on a displayed userinterface 570 that includes application icons 572A-572D displayed inpredefined region 574. In some embodiments, the gesture is detected ontouch-sensitive display 504. The intensity sensors detect the intensityof contacts on touch-sensitive surface 560. The device determines thatthe intensity of contact 562 peaked above the deep press intensitythreshold (e.g., “IT_(D)”). Contact 562 is maintained on touch-sensitivesurface 560. In response to the detection of the gesture, and inaccordance with contact 562 having an intensity that goes above the deeppress intensity threshold (e.g., “IT_(D)”) during the gesture,reduced-scale representations 578A-578C (e.g., thumbnails) of recentlyopened documents for App 2 are displayed, as shown in FIGS. 5F-5H. Insome embodiments, the intensity, which is compared to the one or moreintensity thresholds, is the characteristic intensity of a contact. Itshould be noted that the intensity diagram for contact 562 is not partof a displayed user interface, but is included in FIGS. 5E-5H to aid thereader.

In some embodiments, the display of representations 578A-578C includesan animation. For example, representation 578A is initially displayed inproximity of application icon 572B, as shown in FIG. 5F. As theanimation proceeds, representation 578A moves upward and representation578B is displayed in proximity of application icon 572B, as shown inFIG. 5G. Then, representations 578A moves upward, 578B moves upwardtoward representation 578A, and representation 578C is displayed inproximity of application icon 572B, as shown in FIG. 5H. Representations578A-578C form an array above icon 572B. In some embodiments, theanimation progresses in accordance with an intensity of contact 562, asshown in FIGS. 5F-5G, where the representations 578A-578C appear andmove upwards as the intensity of contact 562 increases toward the deeppress intensity threshold (e.g., “IT_(D)”). In some embodiments, theintensity, on which the progress of the animation is based, is thecharacteristic intensity of the contact. The operations described withreference to FIGS. 5E-5H can be performed using an electronic devicesimilar or identical to device 100, 300, or 500.

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, an “installed application” refers to a softwareapplication that has been downloaded onto an electronic device (e.g.,devices 100, 300, and/or 500) and is ready to be launched (e.g., becomeopened) on the device. In some embodiments, a downloaded applicationbecomes an installed application by way of an installation program thatextracts program portions from a downloaded package and integrates theextracted portions with the operating system of the computer system.

As used herein, the terms “open application” or “executing application”refer to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application is, optionally, any one ofthe following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on;    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6I illustrate examples showing an electronic device 600 havingan operational safety mode in accordance with some embodiments. Theexamples in these figures are used to illustrate the processes describedbelow, including the processes in FIGS. 8-10.

At FIG. 6A, the electronic device 600 is located within an operatingmotor vehicle 602 (e.g., automobile) that is being driven by a user 604(e.g., John 604) of the device 600. While the device 600 is notoperating in the operational safety mode, the device 600 operates in anormal (e.g., default or other non-operational safety mode) mode wherenotifications are outputted without regard to whether they satisfynotification output criteria associated with the operational safetymode. For example, while John is seated in a non-moving vehicle (e.g.,as indicated by the speedometer) at FIG. 6A, an external contact 606(e.g., Jane 606) messages John 604 (e.g., text message) from externalelectronic device 699 (e.g., 100, 300, 500). As shown at FIG. 6A, John'sdevice 600 receives the incoming message and outputs a notification(e.g., “New Message from Jane: Hi John!”). In some cases, outputtingnotifications (e.g., visual, haptic, and/or audible) while a user isoperating a motor vehicle is inconvenient and unsafe, because itdistracts the user from driving.

Turning to FIG. 6B, John is driving in a vehicle travelling at 30 milesper hour (MPH) with device 600 nearby. In FIG. 6B, device 600 is nowoperating in an operational safety mode that manages the output ofcertain notifications. For instance, as discussed below, during theoperational safety mode, only notifications that satisfy notificationoutput criteria are output. As shown at FIG. 6B, Jane 606 sends amessage to John 604 from external device 699 while John is driving, butJohn's device 600 does not display a notification when the messagearrives, because the notification does not meet notification outputcriteria. In some embodiments, John's device 600 remains in a displayoff state. In some embodiments, a benefit of preventing the notificationfrom being displayed (or output by haptic and/or audible outputs) duringthe operational safety mode can be that suppressing notificationsprevents driver distraction. At the same time, the operational safetymode described herein permits notifications corresponding to certain(e.g., critical) messages or alerts to be outputted, thereby preventingthe user from missing important information. Further, the operationalsafety mode provides techniques that allow the user to stay responsiveto certain communications, for example by way of automatic replies. Forease of discussion, the notifications discussed herein correspond tocommunications from external contacts, such as text messages. However,notifications can include alerts corresponding to applications at thedevice (e.g., games, social media) and/or notifications based oninternally generated alerts (e.g., calendar notifications, systemalerts).

In some cases at FIG. 6B, the device 600 enters the operational safetymode when the device 600 detects that it is inside a moving vehicle 602(e.g., while inside a vehicle moving at a speed (e.g., 30 MPH) above apredetermined threshold speed (e.g., 5 MPH)). For example, the device600 detects a motion level based on GPS information (or other locationsensor information), information corresponding to cell towers, and/orWi-Fi information that exceeds a threshold motion level that indicatesthat the vehicle 602 is moving. In some examples, the detected motionlevel is a rate of change of location coordinates and the thresholdmotion level is a threshold rate of changing location coordinates. Insome examples, the detected motion level is a rate of change of Wi-Finetworks or cell towers detected at the device 600 and the thresholdmotion level is a threshold rate of changing Wi-Fi networks. Forexample, the device 600 detects a number of Wi-Fi hotspots movingaround, and/or a number of distinct Wi-Fi networks over a period of timeor a number of cell towers changing over a period of time, which canindicate that the vehicle 602 is driving past numerous Wi-Fi networks.In some examples, the detected motion level and the threshold motionlevel corresponds to a speed or acceleration of the vehicle 602. In someexamples, device 600 accounts for hysteresis to detect if, once thedetected motion level falls below the threshold motion level, that thevehicle 602 is in stop-and-go traffic and should stay in or otherwiseresume the operational safety mode. In some embodiments, device 600determines if contextual parameters are indicative of the electronicdevice being situated within an operating motor vehicle using one ormore techniques described in U.S. Provisional patent application Ser.No. 15/596,592.

In some cases at FIG. 6B, the device 600 enters the operational safetymode when the device 600 detects that it is located within an operatingmotor vehicle based on the output of navigation information. Forexample, the device 600 detects a change of location indicated by anoutput of turn-by-turn instructions from a navigation application at thedevice 600 or from the second electronic device 608.

At FIG. 6B, in some cases, device 600 enters the operational safety modewhen the device 600 detects that it is located within an operating motorvehicle. For example, the device 600 detects that it is connected to asecond electronic device 608 associated with the operating motor vehicle602. In some examples, the second electronic device 608 is a device thatis normally only present in or specific to motor vehicles. For example,the second device 608 is a receiver, head unit, car radio integrated atthe motor vehicle, in-car technology and/or infotainment system such asCarPlay® provided by Apple, Inc. of Cupertino, Calif. In some examples,detecting or connecting to that type of device indicates to the device600 that it is located within the motor vehicle 602. In some examples,the device 600 detects an application or standard that is specific tomotor vehicles at the second electronic device 608 and/or that allowsthe second electronic device 608 to send and/or receive control signalswith the device 600 via the wired or wireless connection. In some cases,the device 600 enters the operational safety mode when the devicereceives a signal from the second device 608 indicating that the motorvehicle 602 is currently in operation.

In some cases at FIG. 6B, the electronic device 600 initiates theoperational safety mode and updates a third party application that thedevice 600 is currently in the operational safety mode. For example, thethird party application is a social media platform and notifying theapplication that the user is currently unavailable may, in practice,enhance the user's experience by providing the information to theapplication, which can tailor its functions to the user's currentsituation (e.g., prevent the user from appearing unresponsive to othercontacts at the application). In some examples, the device 600 instructsa companion device (e.g., 100, 300, 500, and/or a watch connected to thedevice 600) to mirror the operational safety mode.

Still, in some cases at FIG. 6B, the device 600 enters the operationalsafety mode based on manual activation through a user interface (e.g., acontrol center interface) provided at the device 600 or the connectedsecond electronic device 608. In some cases, the manual activationand/or automatic activation that is based on detection of motion levelpermits the device 600 to enter the operational safety mode withoutrequiring connection to the vehicle 602, for instance, if the vehicledoes not have the second electronic device 608.

Further, in some cases at FIG. 6B, the operational safety mode is on oroff (e.g., entered or not) at the device 600 based on conditions shownbelow at Table 1. Table 1 shows examples for prioritizing varioustriggers that cause initiation of the operational safety mode. As shownbelow, the device 600 prioritizes a second set of triggers related toconnection criteria (e.g., whether the device is connected to the secondelectronic device 608) over a first set of triggers related to movementcriteria (e.g., whether the vehicle 602 is moving at or above thethreshold motion level). In some examples, whether the movement criteria(e.g., the first set of operational safety mode initiation criteria) isactive or inactive (e.g., turned off) and whether the connectioncriteria (e.g., the second set of operational safety mode initiationcriteria) is active or inactive is determined based on user selection atthe device 600. In some embodiments, device 600 detects whether thevehicle 602 is moving (e.g., whether the first set of operational safetymode initiation criteria is met) using one or more techniques describedin U.S. Provisional patent application Ser. No. 15/596,592.

TABLE 1 1^(st) criteria active 1^(st) criteria moving not moving notactive 2^(nd) criteria connected ON (1) ON (2) ON (3) active notconnected OFF (4) OFF (5) OFF (6) 2^(nd) criteria not active ON (7) OFF(8) OFF (9)

For example, as shown above, when the device 600 detects that it isconnected to the second electronic device 608, the device enters theoperational safety mode regardless of whether the device 600 detectsthat the vehicle 602 is moving or not and regardless of whether themovement criteria is active or not (e.g., Table 1 at (1)-(3)). Forexample, while the device 600 is connected to the second electronicdevice 608 and satisfies the connection criteria, and the device 600determines that the vehicle 602 is not moving and does not satisfy themovement criteria, the device 600 initiates the operational safety modeanyway. However, when the device 600 detects that the vehicle 602 ismoving and that the connection criteria is not active (e.g., Table 1 at(7)), the device enters the operational safety mode based on satisfyingthe movement criteria. In some embodiments, device 600 determines if thevehicle 602 is moving (e.g., if a level of movement satisfies themovement criteria) using one or more techniques described in U.S.Provisional patent application Ser. No. 15/596,592.

As further shown above, when the device 600 detects that it is notconnected to the second electronic device 608, the device does not enterthe operational safety mode regardless of whether the device 600 detectsthat the vehicle 602 is moving or not and regardless of whether themovement criteria is active or not (e.g., Table 1 at (4)-(6)). Forexample, while the device 600 is not connected to the second electronicdevice 608 and therefore does not satisfy the connection criteria, andthe device 600 determines that the vehicle 602 is moving and satisfiesthe movement criteria, the device 600 does not enter the operationalsafety mode. In practice, prioritizing connection criteria over movementcriteria can help distinguish whether the user is driving his or hervehicle or whether the user is a passenger of a moving vehicle andtherefore may not need the operational safety mode, thereby reducing theinstances of undesired activation of the operational safety mode. Insome cases, when the device 600 detects that the vehicle 602 is notmoving and that the connection criteria is not active (e.g., Table 1 at(8)), the device does not enter the operational safety mode based on notsatisfying the movement criteria. In some embodiments, device 600determines if the vehicle 602 is not moving (e.g., if a level ofmovement does not satisfy movement criteria) using one or moretechniques described in U.S. Provisional patent application Ser. No.15/596,592.

In some embodiments, the device 600 exits the operational safety mode ofFIG. 6B based on detecting that the first and/or set of operationalsafety mode initiation criteria are no longer satisfied (e.g., instantlynot satisfied or continuously not satisfied for a predetermined periodof time), and/or based on manual user request to exit the operationalsafety mode. In some cases, the device 600 continues to initiate theoperational safety mode intelligently based on data collected during alearning period. For example, in some cases, the operational safety modeinitiation criteria are active by default until user selectioninactivates one or more of the operational safety mode initiationcriteria. For example, an operational safety mode learning period isactive when a count for a number of instances the device 600 has enteredthe operational safety mode is below a threshold count. Upon exiting theoperational safety mode, the device 600 displays a feedback screen (notshown) that allows the user to choose whether initiation of theoperational safety mode was intentional or otherwise appreciated (e.g.,receiving selection on a “yes that sounds great” or a “not right now”option). The device 600 detects the user selection rating the experienceand based on the selection, stores data in a learning database andupdates the count by one instance.

In some examples, the feedback screen appears at the end of the firstdrive or first initiation of the operational safety mode and includesinformative text explaining features of the operational safety mode(e.g., the suppression of certain notifications during operationalsafety mode, whether the operational safety mode in that instance wastriggered by connection criteria or movement criteria). In someexamples, the feedback screen allows the user to change settings relatedto the operational safety mode (e.g., whether the detected triggershould continue to be active or inactive, selection of other triggers tobe active or inactive, whitelisting certain contacts for notificationoutput criteria during operational safety mode). In some examples, thefirst detected trigger of a first instance of entering the operationalsafety mode is set as the active trigger unless the user selects toinactivate the trigger (e.g., through settings and/or based on userfeedback during the learning period). In some cases, in response todetermining that the learning database indicates a pattern of repeatedselections corresponding to the “not right now” option, the deviceautomatically deactivates triggering (e.g., or a specific set ofcriteria for triggering) of the operational safety mode. In such cases,the operational safety mode can be reactivated for automatic initiationand/or for manual initiation via general settings or Control Center®provided by Apple, Inc. of Cupertino, Calif.

Turning now to FIGS. 6C-6I, examples for managing the output ofnotifications at device 600 while the device 600 is in the operationalsafety mode of FIG. 6B are shown. In some examples, notificationsoccurring during the operational safety mode are prevented from beingoutput at the device 600 and/or at the second electronic device 608(e.g., by instruction from device 600 to suppress output) unless thenotifications satisfy notification output criteria. For example, at FIG.6C, John's device 600 is in operational safety mode and outputs thenotification corresponding to the message from Jane 606, because Jane isa whitelisted contact such as an emergency contact and/or a favoritescontact that is permitted for notification output. In some examples,notifications corresponding to an application having output permission,a prioritized application (e.g., navigation providing application),and/or a user-selected prioritized application or contact is permittedfor notification output during the operational safety mode.

In some embodiments relating to FIG. 6C, the notification correspondingto Jane's message is output at John's device 600 during the operationalsafety mode, because Jane is a contact having location-sharing access.For example, Jane's device 699 is permitted to acquire locationinformation of John's device 600 based on a location-sharing activestatus or application acknowledged by John and/or John's device 600.

In some embodiments relating to FIG. 6C, the notification correspondingto Jane's message is output at John's device 600 during the operationalsafety mode, because Jane 606 is a recent contact at John's device 600.In some examples, Jane 606 is classified as a recent contact based on arecent communication with Jane 606 (e.g., by phone or text message) thatoccurred within a past predetermined window of time (e.g., within thepast 24 hours) since arrival of the message and/or since initiation ofthe operational safety mode. In some examples, Jane's recency is basedon whether John actively participated in the phone call (e.g., answeredan incoming call, initiated an outgoing call) or sent an outgoing textmessage to the contact within the past predetermined window of time. Insome embodiments, permitting notifications from recent contacts canreduce the instances of missing time-critical messages (e.g.,cancellation of an appointment at the user's driving destination).

Further, in some examples, notifications are output during operationalsafety mode if they correspond to repeated communications from a singlecontact within a window of time (e.g., communications that exceed athreshold number of communication attempts within a predetermined timeperiod). For example, John's device 600 outputs notifications for anincoming call or text message that is a repeated call or text messagefrom a single contact. In some examples, notifications are output duringoperational safety mode if they correspond to an incoming phone call andthe device 600 is Bluetooth integrated with the second electronic device608 that allows answering the call from a button provided at thesteering wheel of the motor vehicle 602. Still, in some examples,notifications are output during operational safety mode if theycorrespond to a system alert indicating a status of the device 600(e.g., battery level alert) or an emergency alert (e.g., emergencyweather alert, government issued alert, AMBER alert).

Referring now to FIGS. 6C-6D, at FIG. 6C, in some examples thenotification corresponding to Jane's message is output at John's device600 during the operational safety mode, because Jane 606 is a contactthat is included in a calendar reminder that is scheduled for at oraround the same time as the arrival of the message. For example, John'sdevice 600 includes a calendar event for lunch at 12:30 pm, with Janelisted as an invitee. Jane's message is received at 12:15 pm and isconsidered to be within an allowed timeframe of the calendar event andtherefore is output. In practice, the device 600 allows criticalcontacts (e.g., based on calendar invitation information and/or recency)to reach the user 604 so that the user does not miss criticalinformation, for example regarding whether a meeting that the user isdriving to is canceled or changed. In some examples, the device 600determines that the notification for Jane's message should be outputbased on GPS information that matches John's direction of travel with adesignated location of the meeting of the calendar invitation. In afurther example as shown at FIG. 6D, external contact 610 (e.g., Emily610) is not an invitee in the calendar invitation and therefore anotification corresponding to her message sent from external device 689at or around the same time as Jane's message (e.g., 12:15 pm) is notoutput at John's device 600. In some cases, notifications that do notsatisfy the notification output criteria are stored for later retrieval(e.g., retrieval through a notifications center when the device hasexited the operational safety mode and/or otherwise is in an unlockedstate, and/or caused for display on a screen such as a locked screenupon exiting the operational safety mode as shown below at locked screen708 of FIG. 7A).

Turning now to FIGS. 6E-6H, in some examples, notifications are outputduring operational safety mode when the notification corresponds to acommunication that includes a notification output request. In someexamples, the notification output request is a request that is selectedby an external user at an external device that requests that the device600 output a notification when the communication from the externaldevice is received. In some examples, the contact requires permission orwhitelisting status from device 600 to attach the notification outputrequest or to make the request effective. In some examples, contactsthat are permitted to receive an automatic reply from the device 600 arepermitted to select the notification output request.

For example as shown at FIG. 6E, an external contact 612 (e.g., Shannon612) messages John 604 from external device 679. John's device 600 is inoperational safety mode and does not display a notificationcorresponding to Shannon's message, because the notification does notmeet notification output criteria. However, Shannon is provided with anautomatic reply in response to her communication being received duringthe operational safety mode. As shown at FIG. 6F, John's device 600responds to Shannon's message automatically by sending an automaticreply to Shannon's device 679. In some examples, the automatic replyincludes text indicating that the user 604 is currently operating themotor vehicle 602 and/or that notifications are currently beingsuppressed or stored for later retrieval. In some examples, theautomatic reply includes a location waypoint of device 600. Further, insome examples, the automatic reply is a user-customized message forspecific classes of contacts, for all contacts that permitted to receiveautomatic replies, or individualized for a particular contact. In somecases, a single automatic reply is provided for any contact that ispermitted to receive the automatic reply. In some examples, theautomatic reply includes instructions for circumventing the suppressionof notifications by providing an explicit notification output request.

Turning to FIG. 6G, subsequent to receiving the automatic reply,external contact Shannon 612 decides that her message is important andshould be output at John's device 600. In this case, Shannon 612 selectsa notification output request to correspond to the previously sentcommunication or to a new communication. A benefit of allowing selectionof the notification output request for the previously sent communicationis that the contact does not have to retype the message in order to haveit requested for output at John's device 600. As shown at FIG. 6G, whenthe message is sent with the selected notification output request (e.g.,selected at a text messaging application used to send the communicationat Shannon's device 679), John's device 600 displays a notificationcorresponding to Shannon's message (e.g., “Hi John! I have anothermeeting and can't make it.”). In some examples, John's device 600indicates whether the notification that is output is being outputbecause it included the notification output request.

In some examples, subsequent to receiving the automatic reply, Shannon612 decides that the message that was sent or a new message being sentis not important for output at this time, and therefore does not selectto attach the notification output request at her device 679. In thatcase, the message sent from Shannon's device 679 is not output fornotification during the operational safety mode at John's device 600, asdemonstrated in the depiction at FIG. 6E. In this way, the notificationoutput request is associated only with a single message that is beingsent from the contact.

Turning to FIG. 6H, in another example, the notification output requestis implemented for a conversation thread between devices 600, 679 ofJohn 604 and Shannon 612, respectively. For example, at FIG. 6H, Shannon612 sends a message to John 604 during the operational safety mode afterShannon's device 679 received the automatic reply, and further afterShannon 612 selected the previous notification output request at FIG.6G. In this case, John's device 600 outputs a new notificationcorresponding to the new message (e.g., “Can we meet tomorrow instead?”)because the notification output request is applied to a remainder of theconversation with Shannon 612. In this case, Shannon 612 does not needto explicitly request the notification output request each time shesends a message to John while John is in the operational safety mode. Insome examples, Shannon's conversation is no longer marked with thenotification output request after inactivity in the message thread for aperiod of time, and/or after the device 600 exits the operational safetymode. In such cases, Shannon 612 would need to reselect the notificationoutput request, in some cases subsequent to receiving another automaticreply, when the device re-enters the same or a new operational safetymode session.

In some examples, the notification output request causes John's device600 to output a notification only when the request is from an externalcontact that is authorized by device 600 to make the notification outputrequest, and/or is authorized to receive automatic replies from device600. In some examples, a contact is authorized to select notificationoutput requests from their device when the contact is authorized toreceive automatic replies, as demonstrated above in foregoing FIGS.6E-6H, when the contact is a recent contact, when the contact haslocation-sharing on with the recipient, and/or when the contact is acalendar invitee corresponding to a calendar event taking place at asimilar or same time. In some examples, contacts are permitted toreceive automatic replies based on one or more of the same foregoingcriteria.

Turning now to FIG. 6I, in some examples, during the operational safetymode, John's device 600 sends an operational safety mode indication toShannon's device 679 when device 600 detects that Shannon 612 is typingthe message to John 604. For example, device 600 provides apresence-indicator to Shannon's device 612 in response to receiving anindication of a potential incoming communication from Shannon's device612. As shown at FIG. 6I, Shannon's device 612 outputs the presenceindicator (e.g., a steering wheel glyph and/or “John is currentlydriving”) to inform Shannon 612 that John 604 is currently driving andtherefore allow Shannon 612 to decide whether to continue to type andsend the message now or later. In some examples, device 600 provides thepresence indicator to all contacts, or to contacts satisfying certaincriteria as noted above, such as contacts that are permitted to receivean automatic reply and/or have location-sharing access. In someexamples, the presence-indicator is provided when both contacts utilizea common messaging platform at their respective devices 600, 679, suchas iMessage (e.g., short messages via services such as SMS and MMS, textmessages via services such as iMessage® provided by Apple, Inc. ofCupertino, Calif.).

FIGS. 7A-7D illustrate exemplary user interfaces for an operationalsafety mode, in accordance with some embodiments. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIGS. 8-10. In FIGS. 7A-7D, the userinterfaces (“UI”) and associated processes are implemented on anelectronic device 700, such as portable multifunction device 100, device300, or device 500.

FIG. 7A shows example user interfaces displayed at device 700 during anoperational safety mode, for example when the device determines that theuser is operating a motor vehicle. The device 700 displays a lockedscreen having an operational safety mode notification indication (atlocked screen 702) and/or banner (at locked screen 704) indicating thatthe device 700 has started a locked session associated with theoperational safety mode. As shown at locked screens 702, 704, and 706,text indications can include, merely by way of example, “Do-Not-Disturbis on while driving. Notifications on locked screen are filtered,”“Currently in Car Mode,” “You're in Car Mode.” In some examples, theoperational safety mode indication banner at locked screen 704 is asticky banner that remains at a top of a list of scrollablenotifications (e.g., notifications that satisfy notification outputcriteria) populated below it.

In some examples, in response to a touch input (e.g., force touch inputhaving a characteristic intensity that that exceeds a first intensitythreshold or a touch sustained for greater than a predetermined amountof time) on the operational safety mode notification banner of lockedscreen 704, the device 700 unlocks. In some examples, in response to thetouch input, the device 700 ends the current locked session and exitsthe operational safety mode. Still, in some examples, in response to thetouch input, the device 700 ends the current locked session and pausesoperational safety mode. In some examples, the touch input provides aquick unlocking gesture. In some examples, the device 700 is unlockedand stays in the operational safety mode subsequent to receiving userconfirmation that the user is currently not operating the vehicle (e.g.,pulled over).

In some examples, in response to the touch input on the operationalsafety mode notification banner, the device displays a first affordance(not shown) that when selected causes the device to end the lockedsession and exit the operational safety mode, and a second affordance(not shown) that when selected causes the device to end the lockedsession and pause the operational safety mode. For example, the firstaffordance corresponds to an “I'm not driving” option to exit theoperational safety mode, and the second affordance corresponds to an“I'm pulled over” option to pause the operational safety mode. In someexamples, a swipe input on the operational safety mode banner revealsthe first and second affordances on locked screen 704. In some cases, apaused operational safety mode and/or locked state automatically resumeswhen driving is detected, for example when contextual parameters satisfycriteria to initiate operational safety mode, as discussed herein.

As further shown at FIG. 7A, in some examples, in response to detectinga user input to unlock the device 700, the device 700 displays aconfirmation affordance without unlocking the device, and in response touser confirmation, unlocks the device. In some examples, unlocking thedevice ends the locked session. For instance, a user input correspondingto an upward swipe on locked screen 704 causes display of a confirmationaction sheet as shown at locked screen 706 that asks the user to confirm“I'm not driving” to exit operational safety mode. In some examples, thedevice 700 temporarily unlocks while remaining in operational safetymode. Still, in some examples, the device 700 permits one unlockingsession per predetermined period of time or operational safety modeperiod. In some examples, the device 700 displays an alternative “I'vepulled over” affordance (not shown) to allow user to access certainfeatures, such as maps and navigation applications, and automaticallyresumes the operational safety mode when driving is detected.

In some examples, in response to receiving user confirmation to unlockthe device 700, the device displays locked screen 708 which shows unreadnotifications, including notifications that were received and not outputduring the operational safety mode (e.g., notifications that did notsatisfy notification output criteria). For example, locked screen 704during the operational safety mode does not show the variousnotifications shown at locked screen 708, which corresponds to a normallocked screen when operational safety mode is not currently implemented.

Still referring to FIG. 7A, in some examples, in response to receivinguser confirmation to unlock the device 700, the device displays homescreen 710 including a plurality of application launch icons that, whenselected, launch their underlying applications. In some examples, thedevice 700 detects user request for a notifications center and displaysthe notifications center (not shown), which includes a first listpreceding a second list, where the first list includes a firstnotification corresponding to a notification that did not satisfy theoutput criteria and was not output during operational safety mode, andthe second list includes one or more notifications (e.g., unreadnotifications) received prior to the locked session (prior to enteringthe operational safety mode). For example, the device 700 provides anotification center that bifurcates between notifications receivedbefore and during the last locked session, and/or during an entireoperational safety mode session. In some examples, the first listincludes notifications suppressed from display.

Further, in some examples, while the device 700 is unlocked, the device700 determines that the set of operational safety mode initiationcriteria is satisfied and enters the operational safety mode byrelocking the device into a second locked session. In some examples,relocking associates the first notification (not shown) at the firstlist with the second list. In some examples, during the second lockedsession, the device 700 receives a second notification (not shown) thatdoes not satisfy the notification output criteria and stores the secondnotification in the notification center. In some examples, storingincludes associating the second notification with the first list. Insome examples, the device 700 detects a subsequent user request tounlock and ends the second locked session. While unlocked, the device700 detects a subsequent user request (e.g., pull-down gesture ordownward swipe on an upper portion of the home screen 710) to displaythe notifications center and displays the first list and the secondlist, where the first list includes the second notification and thesecond list includes the first notification. For example, thenotification center shows notifications received during the last lockedsession. Relocking the device 700 starts over the listing ofnotifications in the first list, for example by moving items in thefirst list (e.g., if still unread) to the second list.

Further in reference to FIG. 7A, while the device 700 is unlocked, thedevice 700 detects a user request to lock the device (e.g., manualactivation) or contextual parameters to initiate operational safety modeand resumes the operational safety mode. In some examples, in responseto the user request and/or detection of contextual parameters thatsatisfy operational safety mode initiation criteria, the device 700displays the locked screen 704 with the operational safety modenotification banner. In some examples, resuming to operational safetymode (e.g., by manual activation through a control center) while stillin the unlocked home screen 710 causes display of the operational safetymode banner (e.g., banner as shown at FIG. 7A, locked screen 704) on thehome screen 710. In some embodiments, device 700 determines ifcontextual parameters are indicative of the electronic device beingsituated within an operating motor vehicle using one or more techniquesdescribed in U.S. Provisional patent application Ser. No. 15/596,592.

Turning to FIGS. 7B-7D, in some examples during the operational safetymode, the device 700 displays a locked user interface 712 including oneor more affordances 714, 716, 718, 720, 722 corresponding to one or moreenabled tasks (e.g., music, navigation, phone, messaging, and voicecontrol). In response to detecting user selection of an affordancecorresponding to an enabled task, the device 700 displays a userinterface corresponding to the enabled task. In some examples, a userselection for an enabled task is a voice command detected at amicrophone. In some examples, the user selection for the enabled task isa touch input on the affordance. As shown at locked user interface 712,the affordances 714, 716, 718, and 720 have larger tap target areas thancorresponding affordances on home screen 710 at FIG. 7A to promote easynavigation. In some examples, the user interface 712 specifically omitssome of the application launch icons from the home screen 710 of FIG. 7Athat are deemed not useful during driving or not safe for use duringdriving. In practice, limiting the options in the operational safetymode allows quicker and easier selection of relevant features, therebyreducing interaction time with the device 700 and reducing the risk ofdriver distraction.

As shown at FIG. 7B, detecting selection of the messaging affordance 720transitions the locked user interface 712 to an inbox user interface 724that includes notifications received during operational safety mode thatsatisfy the notification output criteria. In the current example, thereare three unread notifications which in some examples are furtherindicated as a notification badge (not shown) that indicates the numberof notifications received that satisfy the output criteria. In someexamples, the inbox user interface 724 provides a unified inbox ofmessages from different types of applications corresponding tonotifications from authorized contacts, regardless of the applicationthat the notifications are related to, to promote a people-centricinbox. In some examples, inbox user interface 724 permits replying tocontacts as shown at reply screen 726. In some examples, one or morefunctions provided by the user interfaces 724 and 726 are accessible byvoice control. In some examples, tap target areas for the affordancescorresponding to enabled tasks at the various user interfaces 724, 726are enlarged, as shown at FIG. 7B, to promote easy selection and reducethe risk of driver distraction.

As shown at FIG. 7C, detecting selection of the music affordance 714causes display of a music user interface 728 with various options (e.g.,music, podcasts, radio, audiobooks). In some examples, selection of themusic option causes display of a second music interface 730 thatincludes a quick-play affordance to control output of music and enter amusic control interface 732. In some examples, one or more functionsprovided by music user interfaces 728, 730, 732 are accessible by voicecontrol. In some examples, tap target areas for the affordancescorresponding to enabled tasks at the various user interfaces 728, 730,732 are enlarged, as shown at FIG. 7C, to promote easy selection andreduce the risk of driver distraction.

As shown at FIG. 7D, detecting selection of the navigation affordance716 causes display of a navigation user interface 734 that includes oneor more quick-start navigation affordances to request turn-by-turninstructions for one or more predetermined destinations (e.g., recents,frequent places, location suggestions, favorites, home). Selection of aquick-start navigation affordance provides direction information, forexample as shown at navigation screens 736, 738, and 740. In someexamples, one or more functions provided by navigation user interfaces734, 736, 738, and 740 are accessible by voice control. In someexamples, tap target areas for the affordances corresponding to enabledtasks at the various user interfaces 734, 736, 738, and 740 areenlarged, as shown at FIG. 7D, to promote easy selection and reduce therisk of driver distraction.

As shown at locked user interface 712 at any of FIGS. 7B-7D, detectingselection of the voice control affordance by voice input or touch inputinitiates a voice control task that registers voice input detected atthe microphone for navigating one or more user interfaces during theoperational safety mode. In some examples, the voice control task locksout capabilities that require the device 700 to be unlocked duringoperational safety mode. For example, the voice control denies voicecommands that require full access to the home screen 710 at FIG. 7A, andresponds with an audible output (e.g., “Sorry, I can't help you withthat while you're driving.”)

In some examples, the voice control task enters a verbose operationalmode during the operational safety mode that is distinct from a normaloperational mode when the device is not in operational safety mode.During verbose operational mode, the voice control task provides moreguidance and details for navigating and accomplishing tasks at varioususer interfaces such that the user looks at the display screen lessoften. For example, verbose operational mode confirms when messages aresent and provides additional reminders when normal operational mode doesnot.

In some examples, in response to detecting user selection of the voicecontrol task, the device 700 enables a voice control having a contextspecific for the user interface corresponding to the enabled task. Forexample, the voice control is associated with the user interface that iscurrently being displayed. In some examples, while displaying the userinterface corresponding to the enabled task, the user interface is afirst user interface and the voice control includes a first contextspecific for the first user interface. In response to detecting userinput to display a second user interface, where the second userinterface is different than the first user interface, the device 700transitions display from the first user interface to the second userinterface and updates the voice control with a second context specificfor the second user interface. The second context is different than thefirst context. In some examples, the first and second contexts areassociated with the enabled task (e.g., switching between music-relateduser interfaces 728, 730, 732) or unrelated (e.g., switching from any ofthe music-related user interfaces 728, 730, 732 to any of the navigationuser interfaces 734, 736, 738, 740). In some examples, swiping on a userinterface changes the contexts for voice control as the user interfacesare changed. In some examples, what is displayed on the screen definesthe context for voice commands. In some examples, the context of thevoice control includes reversible steps in a flow of voice commands,including reversible steps between different user interfaces of relatedenabled tasks or unrelated enabled tasks.

In some examples, while the voice control is enabled, the device 700determines an audio range for voice detection at the microphone andautomatically modifies an acoustic model to adapt the voice detection tothe determined audio range. Merely by way of example, the device 700listens for voice commands while the device 700 is placed in a cupholder inside the operating motor vehicle.

FIG. 8 is a flow diagram illustrating a method for an operational safetymode using an electronic device in accordance with some embodiments.Method 800 is performed at a device (e.g., 100, 300, 500) with adisplay. Some operations in method 800 are, optionally, combined, theorder of some operations are, optionally, changed, and some operationsare, optionally, omitted.

As described below, method 800 provides an intuitive way forimplementing an operational safety mode that can include filtering theoutput of notifications when certain contextual parameters are detected(e.g., contextual parameters that indicate a user of the device isdriving). The method reduces the cognitive burden on a user for managingthe output of notifications, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a user to managing the output of notifications faster and moreefficiently conserves power and increases the time between batterycharges.

At block 802, the electronic device detects one or more contextualparameters. In some examples, detected contextual parameters include oneor more of a connection status of the device (e.g., whether the deviceis connected to another electronic device (e.g., second electronicdevice 608) having certain capabilities or characteristics), motion ofthe device (e.g., GPS data or Wi-Fi antenna data indicative of motion),or change in location of the device (e.g., GPS data indicative of achange in location).

In accordance with some embodiments, the contextual parameters include aconnection status that indicates that the device is connected to asecond electronic device (e.g., second electronic device 608) associatedwith the operating motor vehicle (e.g., operating motor vehicle 602) andthe contextual parameters are indicative of the electronic device beingsituated within an operating motor vehicle (e.g., operating motorvehicle 602) (e.g., automobile, motorcycle, aircraft, boat, bicycle). Insome examples, the device is connected to an application at the secondelectronic device (e.g., second electronic device 608) that can send andreceive control signals with the device. In some examples, the device iswirelessly connected via Bluetooth and/or Wi-Fi to the second electronicdevice (e.g., second electronic device 608), and/or wire-connected viaUSB port and/or lightning cable to the second electronic device (e.g.,second electronic device 608).

In accordance with some embodiments, the contextual parameters include amotion level that exceeds a threshold motion level and the contextualparameters are indicative of the electronic device being situated withinan operating motor vehicle (e.g., operating motor vehicle 602). In someexamples, the motion level is a rate of change of location coordinatesdetected at the device and the threshold motion level is a thresholdrate of changing location coordinates. For example, the motion level isbased on GPS or other location sensor information. In some examples, themotion level is a rate of change of Wi-Fi networks detected at thedevice and the threshold motion value is a threshold rate of changingWi-Fi networks. For example, the device detects a number of Wi-Fihotspots moving around and/or a number of distinct Wi-Fi networks over apredefined period of time. In some examples, the detected contextualparameter and/or corresponding criterion of the operational safety modeinitiation criteria accounts for hysteresis to detect if, once themotion level falls below the threshold motion level, the motion levelpicks up again (e.g., during stop and go traffic).

In accordance with some embodiments, the contextual parameters include alocation status that indicates a change of location detected at thedevice and the contextual parameters are indicative of the electronicdevice being situated within an operating motor vehicle (e.g., operatingmotor vehicle 602). For example, a GPS navigation application at thedevice is outputting turn-by-turn instructions for driving to adestination.

In accordance with some embodiments, in response to detecting the one ormore contextual parameters, the electronic device determines whether thedetected one or more contextual parameters satisfy the operationalsafety mode initiation criteria. In some examples, in accordance withthe determination that operational safety mode initiation criteria aresatisfied, the device updates a third party application with a drivingstatus. In some examples, in accordance with the determination thatoperational safety mode initiation criteria are satisfied, the deviceinstructs a companion device (e.g., 100, 300, 500, and/or a smart watch)to mirror the operational safety mode. In some embodiments, theelectronic device (e.g., device 600) determines if contextual parametersare indicative of the electronic device being situated within anoperating motor vehicle using one or more techniques described in U.S.Provisional patent application Ser. No. 15/596,592.

In accordance with some embodiments, while the electronic device is inthe operational safety mode, the device automatically exits theoperational safety mode in accordance with a determination thatoperational safety mode initiation criteria are no longer satisfied. Insome examples, the device receives a manual request to exit. Forexample, the device receives a user request to unlock the device duringoperational safety mode, and in response to the user request, providesan option to exit (e.g., FIG. 7A) the operational safety mode or topause the operational safety mode, and unlocks accordingly. In someembodiments, the electronic device (e.g., device 600) determines ifcontextual parameters are indicative of the electronic device no longerbeing situated within an operating motor vehicle using one or moretechniques described in U.S. Provisional patent application Ser. No.15/596,592.

In accordance with some embodiments, while the electronic device is in asecond mode that is not the operational safety mode, the device receivesa second notification, and in response to receiving the secondnotification, without regard to whether the second notificationsatisfies the set of notification output criteria, the device causesoutput corresponding to the second notification. For example, the deviceoperates in a default and/or normal mode where notifications are output.

At block 804, in accordance with the one or more contextual parameterssatisfying operational safety mode initiation criteria, including acriterion that is satisfied when the contextual parameters areindicative of the electronic device being situated within an operatingmotor vehicle (e.g., operating motor vehicle 602), the electronic deviceinitiates an operational safety mode. Initiating the operational safetymode in accordance with contextual parameters satisfying operationalsafety mode initiation criteria allows the user to quickly engage theoperational safety mode at the device and enables the user to focus onoperating a motor vehicle, thereby promoting safe usage of the device.Performing an operation when a set of conditions has been met withoutrequiring further user input enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to provide proper inputs and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently

At block 806, while the device is in the operational safety mode, theelectronic device receives a notification. For example, the devicereceives a notification and/or communication from an external device(e.g., external device 699, 689, 679). In some examples, the devicereceives a notification and/or alert that is internally generated, forexample a calendar reminder notification and/or a system alert.

In accordance with some embodiments, at block 808, in response toreceiving a notification, the electronic device determines whether thenotification satisfies the set of notification output criteria.

In accordance with some embodiments, the set of notification outputcriteria includes a criterion that is satisfied when the notification isfrom an authorized source. For example, the authorized source is awhitelisted contact, an emergency contact, a favorites contact, anapplication that has output permission, and/or a prioritized applicationsuch as navigation app or a user-selected prioritized application.

In accordance with some embodiments, at block 810, the set ofnotification output criteria includes a criterion that is satisfied whenthe notification corresponds to a communication from arecently-communicated contact. For example, the recency of the contactis based on whether a phone, text, or any other active communicationwith the contact occurred in the past predetermined window of time(e.g., past 24 hours) since arrival of the communication, and/or sincethe most recent initiation of the operational safety mode at the device.Allowing notifications from a recent contact to be output while in theoperational safety mode allows the user to stay informed while the useris on their way to meet the recent contact in some examples.

In accordance with some embodiments, at block 812, the set ofnotification output criteria includes a criterion that is satisfied whenthe notification corresponds to a communication from a contact that isauthorized to receive location information from the device. For example,location sharing with the contact, and/or with an external deviceassociated with the contact, is currently on and/or is grantedpermission. Allowing notifications to be output from a contact havinglocation-sharing access while in the operational safety mode furtherpromotes safe usage of the device while operating a vehicle by allowingthe source of the incoming communication to determine whether to sendthe communication at a later time (e.g., in the event the source hasascertained the device's location) when the user is not operating thevehicle or whether the communication is important and relevant to theuser at the time, thereby allowing the user to stay informed while stillin operational safety mode.

In accordance with some embodiments, the set of notification outputcriteria includes a criterion that is satisfied when the notificationcorresponds to a communication that is a repeated communication from asingle contact. For example, the communication is an incoming call thatis a repeated call from a single contact.

In accordance with some embodiments, the set of notification outputcriteria includes a criterion that is satisfied when the notificationcorresponds to an incoming call and the device is connected to thesecond electronic device (e.g., second electronic device 608) associatedwith the operating motor vehicle (e.g., operating motor vehicle 602). Insome examples, the incoming call is not suppressed in the operationalsafety mode when a detected contextual parameter is a connection statusthat indicates that the device is Bluetooth-integrated with theoperating motor vehicle (e.g., operating motor vehicle 602). Forexample, the device permits answering calls (e.g., from any contact)with a button (e.g., physical button) that is provided on a steeringwheel at the operating motor vehicle (e.g., operating motor vehicle602).

In accordance with some embodiments, the set of notification outputcriteria includes a criterion that is satisfied when the notificationcorresponds to a communication from a contact associated with a calendarevent that coincides with a window of time in which the device is in theoperational safety mode. For example, the communication is an incomingmessage from a contact that is included in a meeting invite at or aroundthe same time as the time that the operational safety mode isimplemented at the device. In some examples, the criterion is furthersatisfied based on matching a location included in the meeting invitewith a detected direction of travel at the device. Allowingnotifications from a contact included in a coinciding meeting invite tobe output while in the operational safety mode allows the user to stayinformed while the user is on their way to a meeting with the contact insome examples.

In accordance with some embodiments, the set of notification outputcriteria includes a criterion that is satisfied when the notificationcorresponds to a system alert. For example, the system alert is a CMOSalert.

In accordance with some embodiments, the set of notification outputcriteria includes a criterion that is satisfied when the notificationcorresponds to an emergency alert. For example, the emergency alert is agovernment alert and/or weather alert.

At block 814, while the electronic device is in the operational safetymode, in accordance with a determination that the notification satisfiesa set of notification output criteria, the device causes outputcorresponding to the notification. For example, the device issues avisual output (e.g., causes display of a notification on the displayscreen and/or at another display screen associated with the secondelectronic device (e.g., second electronic device 608), haptic output,and/or audible output.

At block 816, while the electronic device is in the operational safetymode, in accordance with a determination that the notification does notsatisfy the set of notification output criteria, the device forgoescausing output corresponding to the notification. For example, thedevice suppresses the notification by preventing the notification frombeing displayed at the device, such as from appearing on a locked screenmode, and/or prevents audible or haptic outputs from being issued.

In accordance with some embodiments, in accordance with thedetermination that the notification does not satisfy the set ofnotification output criteria, the electronic device stores thenotification. For example, unread notifications including notificationsthat did not satisfy the notification output criteria are stored forlater retrieval in unlocked state.

Note that details of the processes described above with respect tomethod 800 (e.g., FIG. 8 are also applicable in an analogous manner tothe methods described below. For example, method 900 optionally includesone or more of the characteristics of the various methods describedabove with reference to method 800. For example, method 900 can furtherinclude detecting one or more contextual parameters (e.g., block 802,FIG. 8) and/or in accordance with one or more contextual parameterssatisfying operational safety mode initiation criteria, including acriterion that is satisfied when the contextual parameters areindicative of the electronic device being situated within an operatingmotor vehicle, initiating an operational safety mode (e.g., block 804,FIG. 8). For brevity, these details are not repeated below.

FIG. 9 is a flow diagram illustrating a method for an operational safetymode using an electronic device in accordance with some embodiments.Method 900 is performed at a device (e.g., 100, 300, 500) with adisplay. Some operations in method 900 are, optionally, combined, theorder of some operations are, optionally, changed, and some operationsare, optionally, omitted.

As described below, method 900 provides an intuitive way forimplementing an operational safety mode that can include suppressingnotifications for communications unless they include a sender-markedoutput request (e.g., an explicit request while the device is in anoperational safety mode that otherwise suppresses notifications). Themethod reduces the cognitive burden on a user for managing the output ofnotifications. For battery-operated computing devices, enabling a userto managing the output of notifications faster and more efficientlyconserves power and increases the time between battery charges.

At block 902, while in an operational safety mode, the electronic devicereceives a communication from a contact. For example, the communicationis a text message, phone call, email, or other communication via athird-party application from the contact.

In accordance with some embodiments, while in operational safety mode,in response to receiving an indication of an incoming communication froma source and prior to receiving the incoming communication at thedevice, the electronic device sends a status to the source (e.g., to thesource electronic device, which could be any of devices 100, 300, 500,and/or external device 699, 689, 679) indicating that the device is inthe operational safety mode. Merely by way of example, the device sendsa status such as a presence-indicator to the source indicating that thedevice is in the operational safety mode, that the user of the device iscurrently driving, and/or a location of the device. For example, thedevice receives an indication of a user typing a message in iMessage(e.g., short messages via services such as SMS and MMS, text messagesvia services such as iMessage® provided by Apple, Inc. of Cupertino,Calif.) at the user's device, and sends to the source device (e.g.,external device 699, 689, 679) status information that causes display ofthe status (e.g., steering wheel icon and/or text such as, “User iscurrently driving”). In some examples, the device sends the status toany source of the indication of the incoming communication and/or topermitted sources (e.g., auto-reply sources) only. Sending the status tothe source (e.g., external device 699, 689, 679) prior to receiving theincoming communication further promotes safe usage of the device whileoperating a vehicle by allowing the source of the incoming communicationto determine whether to send the communication at a later time when theuser is not operating the vehicle.

In accordance with some embodiments, at block 904, in response toreceiving the communication from the contact, the electronic devicedetermines whether the communication satisfies notification outputcriteria.

In accordance with some embodiments, while the electronic device is in asecond mode that is not the operational safety mode, the device receivesa second communication, and in response to receiving the secondcommunication, without regard to whether the second communicationsatisfies the set of notification output criteria, the device causesoutput corresponding to the second communication.

In accordance with some embodiments, the notification output criteriainclude a criterion that is satisfied when the contact is a recentcontact that was recently communicated within a past predeterminedwindow of time. For example, recency of the contact is based on a phoneor text communication that occurred in the past 24 hours. In someexamples, after the contact's recency expires, the device receivesanother communication from the contact while the device is inoperational safety mode, and forgoes outputting the notificationregardless of whether the notification output request is included.

In accordance with some embodiments, the notification output criteriainclude a criterion that is satisfied when the contact is an authorizedcontact for selecting the notification output request for thecommunication. In some examples, the contact is authorized to includethe notification output request if the contact received an auto-reply toa previous message. In some examples, the contact is authorized toinclude the notification output request if the contact is auser-designated contact (e.g., a whitelisted contact, no contact,favorites, recents, and/or all contacts).

In accordance with some embodiments, at block 906, the notificationoutput criteria includes a criterion that is satisfied when the contactis an authorized contact for receiving an automatic reply from thedevice in response to a previous communication from the contact.

In accordance with some embodiments, the authorized contact is a recentcontact that was recently communicated within a past predeterminedwindow of time.

In accordance with some embodiments, the authorized contact is auser-designated authorized contact (e.g., a whitelisted contact, nocontact, favorites, recents, and/or all contacts).

In accordance with some embodiments, the authorized contact is a contactthat is authorized to receive current location information correspondingto the device. For example, the contact has location-sharing access tothe device.

In accordance with some embodiments, the authorized contact is a contactassociated with a calendar event that coincides with a window of time inwhich the device is in the operational safety mode. For example, thecommunication is an incoming message from a contact that is included ina meeting invite at or around the same time as the time that theoperational safety mode is implemented at the device. In some examples,the criterion is further satisfied based on matching a location includedin the meeting invite with a detected direction of travel at the device.

At block 908, while in an operational safety mode, in accordance with adetermination that the communication satisfies notification outputcriteria, including a criterion that is satisfied when the communicationincludes a notification output request (e.g., an explicit request,selected at the sending device, that requests that the notificationshould be outputted). the electronic device outputs a notificationcorresponding to the communication. For example, the device displays thenotification and/or issues an audible or haptic output.

At block 910, while in an operational safety mode, in accordance with adetermination that the communication does not satisfy the notificationoutput criteria, the electronic device forgoes outputting thenotification.

In accordance with some embodiments, at block 912, in accordance with adetermination that the communication is a first communication from thecontact and the contact is an authorized contact for receiving anautomatic reply from the device, while not satisfying the notificationoutput criteria (e.g., forgoing outputting the notification), theelectronic device sends an automatic reply to the external deviceassociated with the contact. In some examples, the communication is atext message and the automatic reply is a text message. Sending anautomatic reply allows the user at the device to avoid appearingunresponsive and in some cases further promotes safe usage of the deviceby informing the contact that is unavailable at the time (e.g., when theautomatic reply indicates that user is currently driving), therebyallowing the contact to determine whether to continue attempting toreach the user now or at a later time.

In accordance with some embodiments, the automatic reply includes acurrent location (e.g., location waypoint) detected at the device inresponse to receiving the communication. In some examples, the automaticreply is user customizable for specific classes of contacts, for allcontacts permitted to receive auto-replies, and/or for particularcontact. In some examples, the automatic reply is single reply that isutilized for all permitted contacts.

In accordance with some embodiments, the automatic reply includes textindicating the device is in the operational safety mode. For example,the text indicates that the user is currently driving and/ornotifications are currently suppressed at this time. In some examples,the text indicates other means for reaching the user if necessary (e.g.,call to reach the user when Bluetooth integration is detected thatallows incoming calls to be output).

In accordance with some embodiments, at block 914, while in theoperational safety mode and subsequent to sending the automatic reply,the electronic device receives a second communication from the contact.In accordance with a determination that the second communicationincludes a second notification output request, the device outputs asecond notification corresponding to the second communication, and inaccordance with a determination that the second communication does notinclude the second notification output request, the device forgoesoutputting the second notification. In some examples, the secondcommunication is the first communication with a second notificationoutput request. For example, the contact does not need to retype theprevious message that did not get output, but only flags the previousmessage for output.

In accordance with some embodiments, while in the operational safetymode and subsequent to sending the automatic reply, the electronicdevice receives a third communication from the contact that does notinclude the notification output request and outputs a third notificationcorresponding to the third communication. For instance, in some examplesthe notification output request flags an entire conversation with thecontact to be output during the current operational safety mode.

Note that details of the processes described above with respect tomethod 900 (e.g., FIG. 9 are also applicable in an analogous manner tothe methods described above and below. For example, method 1000optionally includes one or more of the characteristics of the variousmethods described above with reference to method 800. For example,method 1000 can include, while in an operational safety mode, receivinga communication from a contact (e.g., block 902, FIG. 9) and inaccordance with a determination that the communication satisfiesnotification output criteria, including a criterion that is satisfiedwhen the communication includes a notification output request,outputting a notification corresponding to the communication (e.g.,block 908, FIG. 9). For brevity, these details are not repeated below.

FIG. 10 is a flow diagram illustrating a method for an operationalsafety mode using an electronic device in accordance with someembodiments. Method 1000 is performed at a device (e.g., 100, 300, 500)with a display. Some operations in method 1000 are, optionally,combined, the order of some operations are, optionally, changed, andsome operations are, optionally, omitted.

As described below, method 1000 provides an intuitive way forimplementing and/or otherwise initiating an operational safety mode. Themethod reduces the cognitive burden on a user for managing the output ofnotifications, thereby creating a more efficient human-machineinterface. For battery-operated computing devices, enabling a user tomanage the output of notifications faster and more efficiently conservespower and increases the time between battery charges.

At block 1002, while a first set of operational safety mode initiationcriteria of a plurality of sets of operational safety mode initiationcriteria is active, the first set of operational safety mode initiationcriteria including a criterion that is satisfied when movement of theelectronic device (e.g., a rate of motion, a rate of acceleration)exceeds a threshold movement value, the electronic device detects afirst set of one or more contextual parameters. In some examples, thedetected contextual parameters include one or more of a connectionstatus of the device (e.g., whether the device is connected to anotherelectronic device (e.g., second electronic device 608) having certaincapabilities), motion of the device (e.g., GPS data or WiFi antenna dataindicative of motion), or change in location of the device (e.g., GPSdata indicative of a change in location).

At block 1004, while a first set of operational safety mode initiationcriteria of a plurality of sets of operational safety mode initiationcriteria is active, the first set of operational safety mode initiationcriteria including a criterion that is satisfied when movement (e.g.,motion level) of the electronic device (e.g., a rate of motion, a rateof acceleration) exceeds a threshold movement value (e.g., thresholdmotion level), in response to detecting the first set of one or morecontextual parameters, and in accordance with a determination that thefirst set of contextual parameters satisfy the first set of operationalsafety mode initiation criteria, the electronic device initiates theoperational safety mode. In some examples, the determination regardingthe first set of contextual parameters is made without regard to whethera second set of operational safety mode initiation criteria is satisfiedor not. In some embodiments, device 600 determines if contextualparameters are indicative of the electronic device being situated withinan operating motor vehicle (e.g., determines whether the first set ofoperational safety mode initiation criteria are satisfied) using one ormore techniques described in U.S. Provisional patent application Ser.No. 15/596,592.

In accordance with some embodiments, while the second set of operationalsafety mode initiation criteria is not active, and in accordance withthe determination that the first set of operational safety modeinitiation criteria is satisfied, the electronic device initiates theoperational safety mode (e.g., connection criteria is inactive, and thevehicle is detected as moving). In accordance with the determinationthat the first set of operational safety mode initiation criteria is notsatisfied, the device forgoes initiating the operational safety mode(e.g., connection criteria is inactive, and the vehicle is detected asnot moving).

At block 1006, while a second set of operational safety mode initiationcriteria of the plurality of sets of operational safety mode initiationcriteria is active, the second set of operational safety mode initiationcriteria including a criterion that is satisfied when the electronicdevice is connected to a second electronic device (e.g., secondelectronic device 608) associated with an operating motor vehicle (e.g.,operating motor vehicle 602), the device detects a second set of one ormore contextual parameters. In some examples, the second electronicdevice (e.g., second electronic device 608) is a device that is normallyonly present in or specific to motor vehicles (e.g., a receiver, headunit, car radio integrated at the motor vehicle, in-car technology andinfotainment systems such as CarPlay® provided by Apple, Inc. ofCupertino, Calif.) such that detecting or connecting to that type ofdevice is indicative that the device is located in the motor vehicle. Insome examples, the second electronic device (e.g., second electronicdevice 608) includes an application or standard that is specific tomotor vehicles that allows the second electronic device (e.g., secondelectronic device 608) to send and/or receive control signals with thedevice via wired or wireless connections, such as Bluetooth, Wi-Fi, andUSB, and/or includes other features that facilitate linking the device,which may be a portable communications device such as a mobile phone, tothe motor vehicle. In some examples, the detected contextual parametersinclude one or more of a connection status of the device (e.g., whetherthe device is connected to another electronic device having certaincapabilities), motion of the device (e.g., GPS data or WiFi antenna dataindicative of motion), or change in location of the device (e.g., GPSdata indicative of a change in location).

At block 1008, while a second set of operational safety mode initiationcriteria of the plurality of sets of operational safety mode initiationcriteria is active, the second set of operational safety mode initiationcriteria including a criterion that is satisfied when the electronicdevice is connected to a second electronic device (e.g., secondelectronic device 608) associated with a motor vehicle, in response todetecting the second set of one or more contextual parameters, and inaccordance with a determination that the second set of contextualparameters satisfy the second set of operational safety mode initiationcriteria, the device initiates the operational safety mode. For example,the device initiates the operational safety mode regardless of whetherthe first set of operational safety mode initiation criteria is active,inactive, satisfied, not satisfied, or any combination thereof. Asdiscussed above, in some examples, the second electronic device (e.g.,second electronic device 608) is a device that is normally only presentin or specific to motor vehicles (e.g., a receiver, head unit, or carradio integrated at the motor vehicle) such that detecting or connectingto that type of device is indicative that the device is located in themotor vehicle.

In accordance with some embodiments, in accordance with thedetermination that the second set of contextual parameters satisfy thesecond set of operational safety mode initiation criteria, theelectronic device initiates the operational safety mode without regardto whether the first set of operational safety mode initiation criteriais satisfied (e.g., connected and moving) or not satisfied (e.g.,connected and not moving). In some examples, the device initiates theoperational safety mode further without regard to whether the first setof operational safety mode initiation criteria (e.g., movement criteria)is active or inactive.

In accordance with some embodiments, while the electronic device is inthe operational safety mode, the device receives a first notification.For example, the device receives a notification and/or communicationfrom an external device (e.g., external device 699, 689, 679). In someexamples, the device receives a notification and/or alert that isinternally generated, for example a calendar reminder notificationand/or a system alert. In accordance with a determination that the firstnotification satisfies a set of notification output criteria, the devicecauses output corresponding to the first notification. For example, thedevice issues a visual output (e.g., causes display of a notification onthe display screen and/or at another display screen associated with thesecond electronic device (e.g., second electronic device 608), hapticoutput, and/or audible output. In accordance with a determination thatthe first notification does not satisfy the set of notification outputcriteria, the device forgoes causing output corresponding to the firstnotification. For example, the device suppresses the notification bypreventing the notification from being displayed at the device and/orsecond electronic device, such as from appearing on a locked screenmode, and/or prevents audible or haptic outputs from being issued.

At block 1010, while a second set of operational safety mode initiationcriteria of the plurality of sets of operational safety mode initiationcriteria is active, the second set of operational safety mode initiationcriteria including a criterion that is satisfied when the electronicdevice is connected to a second electronic device (e.g., secondelectronic device 608) associated with a motor vehicle, in response todetecting the second set of one or more contextual parameters, and inaccordance with a determination that the second set of contextualparameters do not satisfy the second set of operational safety modeinitiation criteria, while satisfying the first set of operationalsafety mode initiation criteria, the device forgoes initiating theoperational safety mode. For example, a connection status of the devicesupersedes a movement level of the device in regard to whether toinitiate the operational safety mode. As discussed above, in someexamples, the second electronic device (e.g., second electronic device608) is a device that is normally only present in or specific to motorvehicles (e.g., a receiver, head unit, or car radio integrated at themotor vehicle) such that detecting or connecting to that type of deviceis indicative that the device is located in the motor vehicle.

In accordance with some embodiments, in accordance with thedetermination that the second set of contextual parameters does notsatisfy the second set of operational safety mode initiation criteria,the electronic device forgoes initiating the operational safety modewithout regard to whether the first set of operational safety modeinitiation criteria is satisfied or not satisfied. For example, thedevice forgoes initiating the operational safety mode when the device isnot connected, regardless of whether the device is detected as moving ornot moving. In some examples, the device forgoes initiating theoperational safety mode further without regard to whether the first setof operational safety mode initiation criteria (e.g., movement criteria)is active or inactive.

In accordance with some embodiments, in response to detecting the secondset of one or more contextual parameters, in accordance with adetermination that the second set of contextual parameters do notsatisfy the second set of operational safety mode initiation criteria,while not satisfying the first set of operational safety mode initiationcriteria, the electronic device forgoes initiating the operationalsafety mode. For example, the second set of contextual parametersindicates the device is not connected and the first set of contextualparameters indicates the device is not moving.

In accordance with some embodiments, while both the first set ofoperational safety mode initiation criteria and the second set ofoperational safety mode initiation criteria are not active, in responseto receiving a manual activation for initiating the operational safetymode, the electronic device initiates the operational safety mode, andin response to a lack of the manual activation, the device forgoesinitiating the operational safety mode. For example, manual activationis turning the operational safety mode on through a control center orsettings at the device.

In accordance with some embodiments, while the electronic device is in asecond mode that is not the operational safety mode, the device receivesa second notification, and in response to receiving the secondnotification, without regard to whether the second notificationsatisfies the set of notification output criteria, the device causesoutput corresponding to the second notification. For example, the deviceoperates in a default and/or normal mode where notifications are output.

In accordance with some embodiments, while a manual setting for manuallyactivating the operational safety mode is enabled, the deviceinactivates the first set of operational safety mode initiation criteriaand the second set of operational safety mode initiation criteria. Forexample, the device inactivates based on a user setting the operationalsafety mode to manual activation through a control panel or controlcenter. In some examples, manual activation deactivates any set triggersfor entering operational safety mode.

In accordance with some embodiments, while the manual setting for theoperational safety mode is not enabled, the first set of operationalsafety mode initiation criteria is active based on a first userselection and the second set of operational safety mode initiationcriteria is active based on a second user selection. For example, usersselect a type of trigger to cause operational safety mode, such asconnection-activated trigger versus automatic (motion level/speed-based)trigger. In some examples, connection-activated trigger detects whetherthe device is connected to in-car technology and infotainment systems,such as CarPlay® provided by Apple, Inc. of Cupertino, Calif.

In accordance with some embodiments, while neither the first set ofoperational safety mode initiation criteria and the second set ofoperational safety mode initiation criteria are active, subsequent to asecond instance of initiating the operational safety mode in response todetecting an initial set of operational safety mode initiation criteriaof the plurality of sets of operational safety mode initiation criteria,the electronic device receives user selection of the initial set ofoperational safety mode initiation criteria as not active. For example,the device receives user setting for inactivating both criteria. In someexamples, the device sets both criteria as not active after receiving anumber of selections for inactivation in response to a number ofprevious sessions engaging operational safety mode, the number exceedinga threshold number.

In accordance with some embodiments, while neither the first set ofoperational safety mode initiation criteria nor the second set ofoperational safety mode initiation criteria are active, subsequent to afirst instance of initiating the operational safety mode in response todetecting an initial set of operational safety mode initiation criteriaof the plurality of sets of operational safety mode initiation criteriaare satisfied, the electronic device receives user selection of theinitial set of operational safety mode initiation criteria as active,wherein the initial set of operational safety mode initiationcorresponds to at least one of the first set of operational safety modeinitiation criteria and the second set of operational safety modeinitiation criteria. For example, the device enters an onboarding modewhere, when no trigger has yet been set as active, the device presentsan option to select the first detected trigger (detected contextualparameters that satisfy the first set of operational safety modeinitiation criteria or the second set of operational safety modecriteria) as the active trigger. In some examples, the first instance ofentering the operational safety mode is the first time that the deviceenters operational safety mode.

Note that details of the processes described above with respect tomethod 1000 (e.g., FIG. 10 are also applicable in an analogous manner tothe methods described above. For example, method 800 optionally includesone or more of the characteristics of the various methods describedabove with reference to method 800. For example, method 800 can include,while a second set of operational safety mode initiation criteria of theplurality of sets of operational safety mode initiation criteria isactive, the second set of operational safety mode initiation criteriaincluding a criterion that is satisfied when the electronic device isconnected to a second electronic device associated with a motor vehicle,detecting a second set of one or more contextual parameters (e.g., block1006, FIG. 10), and/or in response to detecting the second set of one ormore contextual parameters, in accordance with a determination that thesecond set of contextual parameters do not satisfy the second set ofoperational safety mode initiation criteria, while satisfying the firstset of operational safety mode initiation criteria, forgoing initiatingthe operational safety mode (e.g., block 1010, FIG. 10). For brevity,these details are not repeated below.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to provide safeoperation, such as initiating an operational safety mode based ondetected contexts, and managing notifications and communications duringthe operational safety mode to promote safe operation. The presentdisclosure contemplates that in some instances, this gathered data mayinclude personal information data that uniquely identifies or can beused to contact or locate a specific person. Such personal informationdata can include demographic data, location-based data, telephonenumbers, email addresses, twitter IDs, home addresses, data or recordsrelating to a user's health or level of fitness (e.g., vital signsmeasurements, medication information, exercise information), date ofbirth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used toprovide operational safety mode and manage notifications andcommunications during operational safety. Accordingly, use of suchpersonal information data enables users to calculated control of theoperational safety mode and the notifications and communications duringoperational safety mode. Further, other uses for personal informationdata that benefit the user are also contemplated by the presentdisclosure. For instance, health and fitness data may be used to provideinsights into a user's general wellness, or may be used as positivefeedback to individuals using technology to pursue wellness goals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof operating vehicles, the present technology can be configured to allowusers to select to “opt in” or “opt out” of participation in thecollection of personal information data during registration for servicesor anytime thereafter. In another example, users can select not toprovide user data (e.g., GPS data, input data, etc.) associated withoperational safety mode. In yet another example, users can select tolimit the length of time user data is maintained or entirely prohibitthe development of a baseline operational safety mode profile. Inaddition to providing “opt in” and “opt out” options, the presentdisclosure contemplates providing notifications relating to the accessor use of personal information. For instance, a user may be notifiedupon downloading an app that their personal information data will beaccessed and then reminded again just before personal information datais accessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, notificationscan be managed by inferring preferences based on non-personalinformation data or a bare minimum amount of personal information, suchas the content being requested by the device associated with a user,other non-personal information available to the device, or publiclyavailable information.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, content can beselected and delivered to users by inferring preferences based onnon-personal information data or a bare minimum amount of personalinformation, such as the content being requested by the deviceassociated with a user, other non-personal information available to thecontent delivery services, or publically available information.

What is claimed is:
 1. An electronic device, comprising: a display; oneor more processors; and memory storing one or more programs configuredto be executed by the one or more processors, the one or more programsincluding instructions for: while in an operational safety mode:receiving a communication from a contact; in accordance with adetermination that the communication satisfies notification outputcriteria, including a criterion that is satisfied when the communicationincludes a notification output request, outputting a notificationcorresponding to the communication; and in accordance with adetermination that the communication does not satisfy the notificationoutput criteria, forgoing outputting the notification.
 2. The electronicdevice of claim 1, the one or more programs further comprisinginstructions for: in response to receiving the communication from thecontact, determining whether the communication satisfies notificationoutput criteria.
 3. The electronic device of claim 1, the one or moreprograms further comprising instructions for: while the device is in asecond mode that is not the operational safety mode: receiving a secondcommunication; and in response to receiving the second communication,without regard to whether the second communication satisfies the set ofnotification output criteria, causing output corresponding to the secondcommunication.
 4. The electronic device of claim 1, further wherein: thenotification output criteria include a criterion that is satisfied whenthe contact is a recent contact that was recently communicated within apast predetermined window of time.
 5. The electronic device of claim 1,the one or more programs further comprising instructions for: while inoperational safety mode, in response to receiving an indication of anincoming communication from a source and prior to receiving the incomingcommunication at the device, sending a status to the source indicatingthat the device is in the operational safety mode.
 6. The electronicdevice of claim 1, further wherein: the notification output criteriainclude a criterion that is satisfied when the contact is an authorizedcontact for selecting the notification output request for thecommunication.
 7. The electronic device of claim 1, further wherein: thenotification output criteria include a criterion that is satisfied whenthe contact is an authorized contact for receiving an automatic replyfrom the device in response to a previous communication from thecontact.
 8. The electronic device of claim 6, further wherein: theauthorized contact is a recent contact that was recently communicatedwithin a past predetermined window of time.
 9. The electronic device ofclaim 6, further wherein: the authorized contact is a user-designatedauthorized contact.
 10. The electronic device of claim 6, furtherwherein: the authorized contact is a contact that is authorized toreceive current location information corresponding to the device. 11.The electronic device of claim 6, further wherein: the authorizedcontact is a contact associated with a calendar event that coincideswith a window of time in which the device is in the operational safetymode.
 12. The electronic device of claim 6, the one or more programsfurther comprising instructions for: in accordance with a determinationthat the communication is a first communication from the contact and thecontact is an authorized contact for receiving an automatic reply fromthe device, while not satisfying the notification output criteria,sending an automatic reply to the external device associated with thecontact.
 13. The electronic device of claim 12, further wherein: theautomatic reply includes a current location detected at the device inresponse to receiving the communication.
 14. The electronic device ofclaim 12, further wherein: the automatic reply includes text indicatingthe device is in the operational safety mode.
 15. The electronic deviceof claim 12, the one or more programs further comprising instructionsfor: while in the operational safety mode and subsequent to sending theautomatic reply, receiving a second communication from the contact; inaccordance with a determination that the second communication includes asecond notification output request, outputting a second notificationcorresponding to the second communication; and in accordance with adetermination that the second communication does not include the secondnotification output request, forgoing outputting the secondnotification.
 16. The electronic device of claim 12, further wherein:while in the operational safety mode and subsequent to sending theautomatic reply, receiving a second communication from the contact thatdoes not include the notification output request; and outputting asecond notification corresponding to the second communication.
 17. Anon-transitory computer-readable storage medium storing one or moreprograms configured to be executed by one or more processors of anelectronic device with a display, the one or more programs includinginstructions for: while in an operational safety mode: receiving acommunication from a contact; in accordance with a determination thatthe communication satisfies notification output criteria, including acriterion that is satisfied when the communication includes anotification output request, outputting a notification corresponding tothe communication; and in accordance with a determination that thecommunication does not satisfy the notification output criteria,forgoing outputting the notification.
 18. A method, comprising: at anelectronic device with a display: while in an operational safety mode:receiving a communication from a contact; in accordance with adetermination that the communication satisfies notification outputcriteria, including a criterion that is satisfied when the communicationincludes a notification output request, outputting a notificationcorresponding to the communication; and in accordance with adetermination that the communication does not satisfy the notificationoutput criteria, forgoing outputting the notification.